Skip to content

OCPBUGS-67800: fix CVE-2025-65637#363

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.14from
eshulman2:release-4.14
Feb 23, 2026
Merged

OCPBUGS-67800: fix CVE-2025-65637#363
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.14from
eshulman2:release-4.14

Conversation

@eshulman2
Copy link
Copy Markdown
Member

@eshulman2 eshulman2 commented Dec 22, 2025

Update logrus version to 1.9.1 to avoid CVE-2025-65637 issue.

@eshulman2
OCPBUGS-67800: fix CVE-2025-65637
3664737 
Update logrus version to 1.9.1 to avoid CVE-2025-65637 issue.
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 22, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Dec 22, 2025

@eshulman2: This pull request references Jira Issue OCPBUGS-67800, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-67958 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Update logrus version to 1.9.1 to avoid CVE-2025-65637 issue.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested review from gryf and stephenfin December 22, 2025 14:52
@eshulman2
Copy link
Copy Markdown
Member Author

eshulman2 commented Dec 22, 2025

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Dec 22, 2025

@eshulman2: This pull request references Jira Issue OCPBUGS-67800, which is invalid:

  • expected dependent Jira Issue OCPBUGS-67958 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Dec 22, 2025

@eshulman2: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

gryf
gryf reviewed Jan 5, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@gryf gryf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jan 5, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Jan 5, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eshulman2, gryf

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 5, 2026
mandre
mandre reviewed Jan 5, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@mandre mandre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/label backport-risk-assessed
/verified later @eshulman2

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 5, 2026
@eshulman2
Copy link
Copy Markdown
Member Author

eshulman2 commented Feb 23, 2026

/jira refresh
/verified later @eshulman2

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 23, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Feb 23, 2026

@eshulman2: This pull request references Jira Issue OCPBUGS-67800, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-67958 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-67958 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

Requesting review from QA contact:
/cc @xiaojiey

Details

In response to this:

/jira refresh
/verified later @eshulman2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested a review from xiaojiey February 23, 2026 11:47
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Feb 23, 2026

@eshulman2: This PR has been marked to be verified later by @eshulman2.

Details

In response to this:

/jira refresh
/verified later @eshulman2

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 23, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit ea1dc9a into openshift:release-4.14 Feb 23, 2026
4 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Feb 23, 2026

@eshulman2: Jira Issue OCPBUGS-67800 is in an unrecognized state (Closed) and will not be moved to the MODIFIED state.

Details

In response to this:

Update logrus version to 1.9.1 to avoid CVE-2025-65637 issue.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mandre mandre mandre left review comments

@stephenfin stephenfin Awaiting requested review from stephenfin

@xiaojiey xiaojiey Awaiting requested review from xiaojiey

+1 more reviewer

@gryf gryf gryf left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@gryf gryf

@eurijon eurijon

@itzikb-redhat itzikb-redhat

@imatza-rh imatza-rh

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@eshulman2 @openshift-ci-robot @mandre @gryf @eurijon @itzikb-redhat @imatza-rh